home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
pcbevn25.zip
/
PCBEVENT.DOC
< prev
next >
Wrap
Text File
|
1992-06-24
|
34KB
|
811 lines
╓───────────────────────────────────────────────────────────╖
║ Welcome to PCBEvent Version 2.5. ║
║ The Ultimate In PCBoard Event Managers ║
║ Copyright (C) 1992 By David D. Casto ║
║ All Rights Reserved ║
║ ║
║ 6196 Deewood Loop East ║
║ Columbus, Ohio 43229 ║
║ Voice ║
║ (614) 882-0994 ║
║ ║
╙───────────────────────────────────────────────────────────╜
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - II
-----------------------------------------------------------------------------
Table Of Contents:
=================
Cover Page .......................................... I
Table Of Contents ................................... II
Legal Information ................................... 1
Registration ........................................ 2
Program Features .................................... 3
Upgrading ........................................... 3
Installation ........................................ 4-7
Example PCBEvent.dat ................................ 5
Environment Settings ................................ 6
Batch Updating ...................................... 7
Example Board Bat ................................... 7-8
Command Line Operation .............................. 9-10
Once A Month Event .................................. 11-13
Menu Selections ..................................... 13
Files Created And Modified By PCBEvent .............. 14
Comments ............................................ 15
What's New .......................................... 16
Files Included With PCBEvent v2.5 ................... 19
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 1
-----------------------------------------------------------------------------
PCBEvent Version 2.5
The Ultimate In PCBoard Event Managers
* A PCBoard 14.5a Event Utility *
Copyright (C) 1992 by David D. Casto
6196 Deewood Loop East
Columbus, Ohio 43229
Voice
(614) 882-0994
WARNING!!
=======
As with all new software it is * strongly * recommended that you have a
recent backup just in case.
LEGAL:
=====
David Casto hereby disclaims all warranties relating to this
software, whether express or implied, including without limitation any
implied warranties of merchantability or fitness for a particular
purpose. David Casto will not be liable for any special, incidental,
consequential, indirect or similar damages due to loss of data or any
other reason, even if David Casto or an agent of David Casto has been
advised of the possibility of such damages. In no event shall David
Casto liability for any damages ever exceed the price paid for the
license to use software, regardless of the form of the claim. The
person using the software bears all risk as to the quality and
performance of the software.
You are free to distribute this software as long as there are no
modifications to any files in this archive, and the archive has a ZIP AV
from Bulletin Board Systems.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 2
-----------------------------------------------------------------------------
REGISTRATION:
============
You may try PCBEvent for 30 days and if you find PCBEvent easy, and
convenient to use, a registration of $20.00 would be appreciated. If
you do not like this software enough to register it then delete it!
Registration includes:
1) New updates to the software available for download from Blue
Light BBS.
2) User support also available on Blue Light BBS.
3) A Registered Key file that removes "Registered to UNREGISTERED" to
"Registered to Your BBS. All UNREGISTERED begging etc. will be
bypassed with the key file.
5) As an added protection to event times, I have added another FREE
utility available to REGISTERED users. LockDoor will lock a door
XX minuets before an event. LockDoor is included with this archive
but will _NOT_ run without a Registered PCBEvent.key.
6) Optional Author upload of the key file to your BBS. (U.S. and
Canada only)
7) Your peace of mind knowing that you have done the right thing!
*********************************************************************
Key files are downloaded from Blue Light BBS or uploaded to your BBS!
*********************************************************************
Blue Light BBS is located in Columbus, Ohio
(614) 766-9708 14400 BPS
(614) 766-9709 19200 BPS
* Note: Please address all correspondence to David Casto when calling
Blue Light BBS.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 3
-----------------------------------------------------------------------------
PCBEvent FEATURES:
=================
Imagine an event manager that can check all your nodes to be sure that
all events will be ready to run at their scheduled times. PCBEvent can
even do this from your Autoexec.bat! If a node's event time is off it
will change it in a flash.
PCBEvent is like most other event managers but has a lot of needed
extras that the others do not have. Here is a list of some of the
features of PCBEvent.
Built in Event Editor
Easy to set up and use
Built in Mouse support
Makes it's own EVENT.SYS
Unlimited events per day
A per node event status display
Easy to use data entry input fields
Menu interface for routine maintenance
Screen Burn Protection built into the Menu
Eight command line options for batch file operation
Monthly event option to allow for monthly maintenance
Checks the system clock and selects the next logical event
Day selection so you can run an event on the day(s) you want
Has it's own "WAIT" features that will hold your node(s) down
Option to stamp your Caller(x) log with the event start/end times
Intelligent enough to recognize a first time install and helps you get
through the process
A demo key is included with PCBEvent 2.5. This demo key will allow you
to use the software as if it were registered. The key will work for 30
days from the date PCBEvent was compiled.
UPGRADING:
=========
Please read PCBEvent.new BEFORE upgrading to a to this version.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 4
-----------------------------------------------------------------------------
INSTALLATION:
============
Make a directory PCBEvent, place PCBEvent.exe, PCBEvent.key and
PCBEAU.exe in this directory.
*********************************************************************
* Now Type "PCBEAU" to set the PCBEvent.exe attribute to Read Only. *
*********************************************************************
Next type "PCBEvent" and press ENTER. Select option number 1, the set up
for PCBEvent. The first thing it wants to know is how many nodes that you
want to set up. It will then ask you 8 things for each node:
1) Path to Node x PCBoard.dat.
2) Event time.
3) What days to run the event. Place an X in FIRST space for it to run on
Monday, the SECOND space for Tuesday etc.
4) Slide Event if user is On-Line?
5) Minutes prior to suspend activity
6) Disallow uploads prior to event? (Y/N)
7) Minutes prior to event to disallow uploads.
8) First event batch file Path\FileName. Must not be event.bat as this
is created by PCBoard.
Press F10 to save this information. You are done with this node.
Continue until all nodes are done. (For explanations to the above
questions please see your PCBoard Manual. * No two nodes can run the same
batch file at the same time.
Now select option 2, Node Event Editor. Select a node number to
Add/Edit event times. Select one of the six boxes across the bottom of
the screen. [Next] will display the next event in PCBEvent.dat. [Prev]
will select the previous event in PCBEvent.dat. [Edit] will allow you to
edit the event displayed on the screen. [Add] will allow you to add an
event to PCBEvent.dat. [Del] will allow you to delete the event displayed
on the screen. [Quit] will return you to the Main menu.
You may have as many events as you like in the PCBEvent.dat. There will
be a PCBEvent.dat in each node(s) directory. If you would like, you may
edit these files with a text editor.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 5
-----------------------------------------------------------------------------
PCBEvent.dat FORMAT:
===================
Line 1 Number of events
Line 2 First event time
Line 3 Days to run this event. (MON thru SUN)
Line 4 Suspend time in min. (01-59)
Line 5 Slide event. (Y/N)
Line 6 Disallow uploads. (Y/N)
Line 7 Disallow uploads min. (01-59)
Line 8 First Path\FileName.bat of event.bat to run
Line 9 Second event time
Line 10 Days to run this event. (MON thru SUN)
Line 11 Suspend time in min. (01-59)
Line 12 Slide event. (Y/N)
Line 13 Disallow uploads. (Y/N)
Line 14 Disallow uploads min. (01-59)
Line 15 Second Path\FileName.bat of event.bat to run
etc....
Example PCBEvent.dat:
--------------------
3 <--- Number of events
01:00 <--- Event time
XX XXXX <--- Will not run on Wed
01 <--- Suspend time min.
Y <--- Slide event (Y/N)
Y <--- Disallow uploads (Y/N)
20 <--- Disallow uploads min.
C:\PCB\EVENT1.BAT <--- Event batch to run
02:00 <--- Event time
XXXX XX <--- Will not run on Fri
12 <--- Suspend time min.
N <--- Slide event (Y/N)
Y <--- Disallow uploads (Y/N)
22 <--- Disallow uploads min.
C:\PCB\EVENT2.BAT <--- Event batch to run
03:00 <--- Event time
X XXXXX <--- Will not run on Tue
13 <--- Suspend time min.
Y <--- Slide event (Y/N)
Y <--- Disallow uploads (Y/N)
23 <--- Disallow uploads min.
C:\PCB\EVENT3.BAT <--- Event batch to run
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 6
-----------------------------------------------------------------------------
After you have all nodes set up and all the PCBEvent.dat files done
select option 3 from the menu. This is where all the action is. PCBEvent
will read all dat files, sort, re-write them, read in PCBoard.dat and
adjust the next event time to the next logical event time, and even write
the event.sys file for your event(s).
* See the "Once A Month" section for Once A Month events. *
**************************************************************************
Note: PCBEvent will set the event active field to "Y" unless there
is not an event in the PCBEvent.dat that is in the next 24 hour time
frame. This will allow you to not run any events on any day(s). PCBEvent
will stamp the Caller(x) log and PCBEvent.log if it sets the event active
field to "N" informing the sysop that no event(s) will run on this node
for the next 24 hours.
**************************************************************************
ENVIRONMENT SETTINGS:
====================
PCBEvent can be executed from ANY directory if you make the following
changes to your Autoexec.bat and reboot your system. This will omit the
need to Change Directory to the PCBEvent directory before executing
PCBEvent.
Edit your Autoexec.bat and add this line.
SET PCBEvent=E:\PCBEvent
Add the PCBEvent directory to your DOS Path statement in your
Autoexec.bat.
Example Path Statement:
----------------------
Path=C:\;C:\DOS;C:\UTIL;E:\PCBEvent
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 7
-----------------------------------------------------------------------------
BATCH UPDATING:
===============
Edit your Board.bat and add this line.
pcbevent /Nx <--- Adjust node x event time
Place this line in each Node(s) board.bat * before * executing
PCBoard. (Replace x with the Node Number). Example 1 should be used if
the sysop wants PCBEvent to run several times a day. In this example
PCBEvent will run each time a NON Shelled door is executed and after each
drop to DOS. On busy systems I recommend Example 2. If you have had past
problems with lock up's then you should use Example 1.
EXAMPLE 1 BOARD.BAT (for Node 1):
--------------------------------
@echo off
c:
cd\pcb
SET NODE=1
SET PCB=/SWAP/MAIN/RESET/BYTECRED:2/UPCRED:2
if exist remote.bat rename remote.bat remote.sys
if exist event.bat rename event.bat event.sys
if exist door.bat del door.bat
if exist endpcb del endpcb
pcbevent /N1
PCB145
if exist remote.bat remote
if exist door.bat door
if exist event.bat event
if exist endpcb goto end
board
:END
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 8
-----------------------------------------------------------------------------
EXAMPLE 2 BOARD.BAT (for Node 1):
--------------------------------
@echo off
c:
cd\pcb
SET NODE=1
SET PCB=/SWAP/MAIN/RESET/BYTECRED:2/UPCRED:2
if exist remote.bat rename remote.bat remote.sys
if exist event.bat pcbevent /N1 <---- Run PCBEvent here
if exist event.bat del event.bat <---- Delete Event.bat
if exist door.bat del door.bat
if exist endpcb del endpcb
PCB145
if exist remote.bat remote
if exist door.bat door
if exist event.bat event
if exist endpcb goto end
board
:END
*************************************************************************
Notice that you _MUST_ delete event.bat. Since PCBEvent makes a new
Event.sys DOS will _not_ allow you to rename it. If you do not delete it
each time your board.bat cycles it will run your event and could cause
you a lock up!
*************************************************************************
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 9
-----------------------------------------------------------------------------
COMMAND LINE OPERATION:
======================
There are 6 command line switches for use in batch files.
1) PCBEvent /N1
PCBEvent will check, sort and write all of Node 1 files to be sure
the next event will execute when scheduled. Use in your
Board.bat. _DO NOT_ Use in your daily events, as it will remove
your event.bat causing your Node not to re-load.
2) PCBEvent /R
PCBEvent will check, sort and write ALL Nodes files to be sure the
next event will execute when scheduled. _DO NOT_ Use in your
daily events, as it will remove your event.bat causing your Node
not to re-load.
3) PCBEvent /START:1
PCBEvent will stamp the NODE caller logs with the time the event
started.
4) PCBEvent /END:1
PCBEvent will stamp the NODE caller logs with the time the event
ended.
5) PCBEvent /WaitUp:1:500
PCBEvent will wait 500 seconds for Node 1 to return to the board.
If PCBEvent waits for 500 seconds an errorlevel of 10 is returned.
If node 1 returns to the board before the 500 seconds PCBEvent
will return an errorlevel of 0. Seconds may be as high as 999999.
(See example EVENT1.BAT for usage/purpose of the errorlevel)
6) PCBEvent /WaitDown:1:500
PCBEvent will wait 500 seconds for Node 1 to drop to the Event.
If PCBEvent waits for 500 seconds an errorlevel of 10 is returned.
If node 1 drops to the event before the 500 seconds PCBEvent will
return an errorlevel of 0. Seconds may be as high as 999999.
(See example EVENT1.BAT for usage/purpose of the errorlevel)
7) PCBEvent /WaitDownWS:1:2:500
This option is for systems that are running a LAN and have the
PCBoard node directories on workstations and PCBEvent on the
server. This option _must_ be used with WaitUpWS. The SET
PCBEVENT environment path must be available to each workstation.
Node 1 will wait for node 2 to exit PCBoard and run it's event.
It will wait 500 seconds before it will exit. If node 2 has
dropped to the event before the 500 seconds an errorlevel of 0
will be returned. If node 2 does not drop within the xxx seconds
an errorlevel of 10 will be returned. Seconds may be as high as
999999. See example Event2.bat.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 10
-----------------------------------------------------------------------------
8) PCBEvent /WaitUpWS:1:2:500
This option is for systems that are running a LAN and have the
PCBoard node directories on workstations and PCBEvent on the
server. This option _must_ be used with WaitDownWS. The SET
PCBEVENT environment path must be available to each workstation.
Node 1 will wait for node 2 to return to PCBoard. It will wait
500 seconds before it will exit. If node 2 has returned to
PCBoard before the 500 seconds an errorlevel of 0 will be
returned. If node 2 does not return to PCBoard within the 500
seconds an errorlevel of 10 will be returned. Seconds may be as
high as 999999. See example Event2.bat.
*********************************************************************
NOTE: The counter on the WAIT features will have different MAX Time
each time you run them. This is normal and is not a bug in PCBEvent.
*********************************************************************
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 11
-----------------------------------------------------------------------------
ONCE A MONTH EVENT:
==================
PCBEvent can run a "Once A Month" event. This is for those of you
that need to have a special event that does things like Zip the log
files and start fresh for the new month, Pack the User file (Kill the
Users) etc.
PCBEvent will look for a file named PCBEvent.mth in the "SET
PCBEVENT" path/current path. If this file exists PCBEvent will analyze
it's content while processing all events.
Here is a little information to help you understand how this feature
works. With the following you should be able to set up a "Once A
Month" event. I might add - with a little batch file creativity you
could have a "Once A Month" event several times a month.
HOW:
---
This event is a _replacement_ of a normal event not just another
event. You _must_ have a regular event scheduled and the day flags
_must_ be set. If the NODE field of the PCBEvent.mth file does not
equal the NODE number then PCBEvent will continue with the normal event
processing. If the NODE field of the PCBEvent.mth file equals the NODE
number being processed then PCBEvent will continue to analyze the "Once
A Month" event data.
If the DAY field of the PCBEvent.mth file equals today's DAY _AND_
the Time field of the PCBEvent.mth file equals the Next regular event
Time the Batch field in the PCBEvent.mth file will be substituted in
place of the Regular event Batch.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 12
-----------------------------------------------------------------------------
RULES:
-----
1) The TIME field in the PCBEvent.dat file _MUST_ match the TIME
field in the PCBEvent.mth file.
2) The DAYS event field in the PCBEvent.dat file _MUST_ have a flag
(X) for the DAY.
Example:
PCBEvent.mth> 1 <- NODE To Run Event
01 <- DAY To Run
00:02 <- TIME To Run
05 <- Suspend time
N <- Slide event (Y/N)
Y <- Disallow Uploads Prior
10 <- Disallow Uploads Time
c:\pcb\Monthly.bat <- Batch File To Run
PCBEvent.dat> 1 <- Number Of Events
00:02 <- TIME To Run
XXXXXXX <- DAYS Of The WEEK To Run (Mon-Sun)
05 <- Suspend time
N <- Slide event (Yes/No)
Y <- Disallow Uploads Prior
10 <- Disallow Uploads Time
C:\PCB\EVENT1.BAT <- Batch File To Run
Note that the TIME fields in both examples match. Also the "DAYS
To Run" are all flagged (in the PCBEvent.dat), as the 1st of every
month does _NOT_ always fall on a Monday or a Friday.
3) You may have the following differences in your PCBEvent.dat and
PCBEvent.hst:
1) Suspend Time
2) Slide Event If A User Is On-Line.
3) Disallow Uploads Prior To The Event
4) Disallow Uploads Prior To The Event TIME
5) Naturally The Batch File To Run.
If you have any problems setting up your "Once A Month" event
remember I do answer my electronic mail and my voice phone!
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 13
-----------------------------------------------------------------------------
MENU SELECTIONS:
===============
The menu has 6 options. Here is a brief description of each.
1) Configure PCBEvent CHG File
Use to add/edit a nodes path.
2) Node Event Editor
Use to add/edit/delete an event for a node.
3) Update All Nodes
Use to update all nodes event times.
Sort and write all nodes PCBEvent.dat files.
4) Update A Node
Use to update a node event time.
Sort and write a node PCBEvent.dat file.
5) Status of ALL Nodes
Use to see each nodes next event time, status and event batch
file.
6) Toggle Sound Off / On
Use to turn the sound off or on.
6) Exit PCBEvent Manager
Use to exit to DOS.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 14
-----------------------------------------------------------------------------
FILES CREATED AND MODIFIED BY PCBEvent:
======================================
1) PCBoard.dat - Updated with next event data. _DO NOT DELETE_ One in
each node(s) directory.
2) PCBoard.da$ - Backup PCBoard.sys, _DO NOT DELETE_, this is used if
PCBEvent can not find your PCBoard.dat file. One in node(s) each
directory.
3) Event.sys - Updated with next event data. One in each node(s)
directory.
4) Event.sy$ - Backup Event.sys, _DO NOT DELETE_, this is used if
PCBEvent can not find your Event.sys file. One in each node(s)
directory.
5) PCBEvent.dat - Event data, sorted and written from menu operation
only. One in each node(s) directory.
6) PCBEvent.da$ - Backup PCBEvent.dat, _DO NOT DELETE_, this is used if
PCBEvent can not find your PCBEvent.dat file. One in node(s) each
directory.
7) PCBEvent.log - Log of PCBEvent activities for Node(x). Source for
trouble shooting. Delete after reviewing. PCBEvent will not delete.
One in each node(s) directory.
8) PCBEvent.cfg - Stores PCBoard, Node, path, file information. Also
stores some next event information for fast recall. _DO NOT DELETE_
If Deleted you will have to re-configure.
9) Node(X) - A Null file made to signal other nodes that an event
is in progress on node X. Made by WaitDownWS/WaitUpWS command switch.
10) PCBEvent.err - PCBEvent will create if it encounters an error One in
each node(s) directory.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 15
--------------------------------------------------------------------------
COMMENTS:
========
I hope you like this utility and that it saves you lots of headaches.
If you like it PLEASE let me know, and if you want to add to the wish
list, GREAT! If you like it enough to use it then please Register it.
Each registration inspires and keeps this author at the key board.
If you have any problems installing PCBEvent or any of my
utilities/doors, SUPPORT is available on Blue Light BBS. Just (J)oin
conference #99 or feel free to call me voice ( 614-882-0994 ).
NOTE: First time callers to Blue Light BBS
You will be required to complete INSTALED (question and answer door),
when completed you will be automatically placed into PCBVerify. You may
abort the call back. When you return to PCBoard you will be able to
(J)oin conference #99 - Daves-Place.
PLEASE, if you are having a problem upload to me a copy of:
1) PCBEvent.dat
2) PCBEvent.log
3) PCBEvent.err
4) PCBEvent.cfg
5) Autoexec.bat
6) Board.bat
7) Event.sys
8) Anything else that may be of help.
I monitor the DOOR and UTILITY conferences on Salt Air, and the Doors
and PCBHints conferences on the Rime network. Please address all
messages to David Casto.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 16
-----------------------------------------------------------------------------
WHAT'S NEW WITH 2.5
===================
Fixed - PCBEvent would not recognize a new installation if you turned off
the sound before configuring.
Fixed - Would exit if it ran into no events within the next 24 hours.
Fixed - Would exit with an "Error 5" if a user placed one digit in a
minute field in the editor.
Added - Messages to the user to help define input questions. Input errors
are now defined.
Added - Up Arrow, Down Arrow, ESC and F10 keys to the editor. Up Arrow
will advance the input to the prior field. Down Arrow will advance input
to the next field. ESC will exit the editor and return to the Main Menu
without saving changes. F10 will save any changes.
* Added - I have included a utility to set PCBEvent.exe file attribute to
read only. This should clear up some reports of PCBEvent locking up
while multiple nodes run PCBEvent at the same time. It will change
PCBEvent.exe to read only if it is not currently set to read only. It
will also remove the read only attribute if it is currently set to read
only. PCBEvent Attribute Utility (PCBEAU.EXE) MUST be executed in the
same directory as PCBEvent.exe.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 17
-----------------------------------------------------------------------------
WHAT WAS NEW WITH 2.4:
=====================
Added - New data input routines to the editor. When you edit an existing
record the fields will have the previous value. This will save a lot
of needless typing.
Added - Toggle Sound Off / On option to the Main Menu. This option will
allow you turn off ALL sound.
Fixed - Cosmetic changes to the Node Editor.
Fixed - Node Event Status display. It would list 12 nodes (one window)
and no more.
Tested - Due to conflicts with some software and OS2's "DOS" windows, I
tested PCBEvent in this environment and it passed.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 18
-----------------------------------------------------------------------------
WHAT WAS NEW WITH 2.3:
=====================
* Added - Demo key ability. A demo key is included with PCBEvent 2.5. This
demo key will allow you to use the software as if it were registered.
The key will work for 30 days from the date PCBEvent was compiled.
Added - /WaitDownWS:Y:X:xxx switch. This option is for systems that are
running a LAN and have the PCBoard node directories on workstations
and PCBEvent on the server. This option _must_ be used with WaitUpWS.
The SET PCBEVENT environment path must be available to each
workstation. Node Y will wait for node X to exit PCBoard and run it's
event. It will wait xxx seconds before it will exit. If node X has
dropped to the event before the xxx seconds an errorlevel of 0 will be
returned. If node X does not drop within the xxx seconds an
errorlevel of 10 will be returned. See example Event2.bat.
Added - /WaitUpWS:Y:X:xxx switch. This option is for systems that are
running a LAN and have the PCBoard node directories on workstations
and PCBEvent on the server. This option _must_ be used with
WaitDownWS. The SET PCBEVENT environment path must be available to
each workstation. Node Y will wait for node X to return to PCBoard.
It will wait xxx seconds before it will exit. If node X has returned
to PCBoard before the xxx seconds an errorlevel of 0 will be returned.
If node X does not return to PCBoard within the xxx seconds an
errorlevel of 10 will be returned. See example Event1.bat.
Added - Retry when accessing LOCKED files. Will now try 20 times to
access a locked file before aborting.
Improved - File access error routines and logging.
PCBEvent Version 2.5 - PCBEvent.DOC - USER MANUAL Page - 19
-----------------------------------------------------------------------------
FILES INCLUDED WITH PCBEvent v2.5 :
=================================
1) PCBEvent.HST - Example Once A Month Data File
2) PCBEvent.DAT - Example Event Data File
3) PCBEvent.DOC - Your Reading It!
4) PCBEvent.ERR - Example Error Log
5) PCBEvent.EXE - PCBEvent Executable
6) PCBEvent.LOG - Example PCBEvent Activity Log
7) PCBEvent.REG - PCBEvent Registration Form
8) PCBEvent.NEW - PCBEvent What's New With v2.5
9) Caller1 - Example Caller Log
10) Event1.bat - Example Event Batch File
11) Event2.bat - Example Event Batch File (WaitDownWS WaitUpWS)
12) Event.sys - Example Of PCBEvent's Event.sys Creation
13) Monthly.bat - Example Of A Monthly Event Batch File
14) NewMonth.bat - Example Of A Monthly System Event Batch File
15) File_id.diz - Archive Description
16) Lockdor1.zip - LockDoor Program For Registered PCBEvent Owners
17) Blueligh.inf - Information For Access To The Support BBS
18) PCBEAU.EXE - Set PCBEvent.exe Read Only Attribute On/Off
19) PCBEAU.DOC - PCBEAU DOC File.